Component tagging with maintenance related information in open and closed formats

ABSTRACT

A method for maintaining a complex article, including retrieving maintenance information relating to maintenance of a component of a complex article from an electronically-accessible tag coupled to the component and applying the retrieved maintenance information to a determination regarding maintenance of the complex article. A device including a complex article including a first component and a second component, the first and second components being one of individually replaceable and maintainable. The first component is tagged with a first tag that stores first computer accessible information including a first identifier identifying the first component and first maintenance information describing maintenance of the first component. The second component is tagged with a second tag that stores second computer accessible information including a second identifier identifying the second component and second maintenance information describing maintenance of the second component.

BACKGROUND

[0001] This invention relates to maintenance.

[0002] The tagging of articles with computer-readable identifiers andinformation has provided great improvements in areas such as supplychain management, asset tracking and management, security and accesscontrol, transportation, toll collection, baggage handling, inventorycontrol and management, healthcare, and consumer services. For example,bar codes can be used to track the storage and movement of objectsranging from foodstuffs to coupons. Radio frequency identification(“RFID”) tags can be used to track individuals as they access restrictedlocations and services. Smart cards can be used to store insuranceinformation, medical records, and phone accounts. Examples ofcomputer-readable tags include, active and passive RFID tags, integratedcircuit (“IC”) microprocessor cards and memory cards, optical memorycards, barcodes, tags, and smart cards.

SUMMARY

[0003] The present invention provides method and apparatus, includingcomputer-program products, for tagging articles with maintenance relatedinformation. Articles that can be tagged include complex articles andcomponents of complex articles. The phrase ‘complex article’ is used inthis specification to refer to tangible objects and devices that areassembled from individually taggable components. The components areindividually replaceable or maintainable on the complex article.Examples of complex articles include motor vehicles, trains, aircraft,ships, military hardware and vehicles, buildings, and assembly lines.Examples of components include engines, axels, wheels, arms, and bodyframes. Complex articles are physical incarnations formed by one or morephysical components that are amenable to being separately tagged with aunique, computer-readable identifier.

[0004] In general, in one aspect, the invention features systems andmethods, and components configured to perform aspects of the methods,for maintaining complex articles. In one aspect the invention provides amethod for storing maintenance information on anelectronically-accessible tag that is coupled to an article. The methodincludes storing maintenance information in both a first and secondformat in the electronically accessible tag where the first format is inaccordance with an open standard and the second format is in accordancewith a closed standard.

[0005] Aspects of the invention can include one or more of the followingfeatures. The method can include storing maintenance information in aformat that is device independent.

[0006] Storing maintenance information in the first format can includestoring the maintenance information in a format that is in accordancewith one of RTF, ASCII, and PDF. Storing maintenance information in thesecond format includes storing the maintenance information in a formatthat is proprietary and that can only be accessed by proprietarydevices.

[0007] The method can include retrieving the maintenance data, updatingthe format of the maintenance data and storing the maintenance data withthe updated format in the electronically accessible tag. Storingmaintenance data can include storing maintenance procedures andtechnical specifications related to the article. Storing maintenanceinformation can include storing a first type of maintenance informationin the first format and storing a second type of maintenance informationin the second format. Storing a first type of maintenance information inthe first format includes storing maintenance logs in the first formatand storing maintenance procedures and technical specifications in thesecond format. Storing maintenance information can include storingmaintenance information of a component of one of an aircraft, a seagoing vessel, and a vessel that travels on land.

[0008] In another aspect, the invention provides an electronicallyaccessible tag that includes a memory that includes maintenance data ofa first and a second format where the first format is in accordance withan open standard and the second format is in accordance with a closedstandard.

[0009] Aspects of the invention can include one or more of the followingfeatures. The first format can be device independent. The maintenancedata can include maintenance procedures and technical specifications ofan article. The electronically accessible tag can include an input andoutput device for sending maintenance data and receiving updatedmaintenance data, and a processor and logic for updating the first andsecond format. Maintenance data of the first format can includemaintenance logs and maintenance data of the second format can includemaintenance procedures and technical specifications.

[0010] The invention can be implemented to realize one or more of thefollowing advantages. By tagging one or more components of a complexarticle, technical information as well as repair, replacement, and/ormaintenance records for the tagged components can be maintainedseparately from other records and accessed directly on the componentitself. Such tagging greatly simplifies the handling of technicalinformation and maintenance, replacement and/or repair records for thecomplex article, and the tracking of component maintenance as thecomponent moves from location to location. For example, when an aircraftengine component is removed from an airplane and a new engine componentis substituted, the maintenance records for both engine components canremain physically joined to the individual or respective components andaccessible on the components themselves. Moreover, each engine componentretains a tag that identifies the component, allowing an airline totrack the component as it moves from aircraft to aircraft. As anotherexample, when an assembly line is retrofit with a new press, technicalinformation regarding the operation of the press can be stored directlyon the press itself (e.g., in a tag). Thus, when a new computer numericcontrol (“CNC”) component is provided to the press, technicalinformation regarding the interface between the CNC and the press can beretrieved from the tag on the press.

[0011] The tagging of complex articles can be implemented over a widerange of scales. For example, an aircraft can be tagged, an aircraftengine on the aircraft can be tagged, and a turbine of the aircraftengine can be tagged. The type of computer-readable information storedon each component can be adjusted to the nature or operating environmentof the component. For example: the aircraft can be tagged with a uniqueidentifier; the aircraft engine can be tagged with a unique identifier,a log of flight time of the engine, and maintenance records of theengine; and the turbine can be tagged with a unique identifier and theresults of previous non-destructive evaluations of the integrity of theturbine.

[0012] Hierarchical and other relationships can be defined between oramong tracked components and can be used for tracking relationshipsbetween components. For example, an aircraft can be tagged with a tagthat identifies one or more individual engines mounted to the aircraftduring a certain period of time.

[0013] Data for the tags can be received from sensors that sense a traitof the article. Data can also be input from specialized devices designedto write to the component. For example: a tag on an aircraft can receivea time and data stamp from a writing device upon arrival at an airport;a tag on an aircraft engine can receive the flight hours of the enginefrom a sensor that senses the operation of the engine; and a tag on theturbine can receive input from a specialized non-destructive evaluationunit after testing. Tags can also receive information from other datasources, such as, e.g., systems that provide circumstantial informationlike weather, traffic conditions, transportation schedules, and so on.

[0014] The system can be integrated with existing software and hardwaresystems using open interfaces. With such interfaces, the system iscompatible with existing systems without the need for plug-ins orupgrades into the existing systems. For example, the system can provideopen interfaces to integrate virtually every kind of tag, tag reader,scanner, sensor, and application. The system can be implemented toinclude applications that can generically read data from, and write datato, article tags. The system can include generic tracking of real-timetelemetry. The system can integrate existing geographical informationsystems (“GIS”) and data.

[0015] The system can be integrated with existing software and hardwaresystems using closed interfaces. With such interfaces, the system iscompatible only with systems that are licensed to use the closedinterfaces. Such a restriction can prevent data from being accessed andchanged by those not licensed to do so.

[0016] The system facilitates the scheduling and performance ofmaintenance of mobile articles such as airplanes, ships, and trains. Forexample, the system helps an operator determine which maintenance can becompleted when an airplane makes a temporary stop over. Furthermore, thesystem does not need a central system to so facilitates maintenancebecause all the necessary data in stored on the tags. A military vessel,such as a nuclear submarine, operating at a remote locale thus need notcommunicate with a base to retrieve maintenance information and,advantageously, is able to maintain radio silence.

[0017] The details of one or more embodiments of the invention are setforth in the accompanying drawings and the description below. Otherfeatures, objects, and advantages of the invention will be apparent fromthe description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

[0018]FIG. 1 shows an example of a complex article that is tagged.

[0019]FIG. 2 shows an example of a unique identification code.

[0020]FIGS. 3, 4, and 5 show examples of maintenance information thatcan be stored on a tag.

[0021]FIG. 6 shows another example of a complex article that is tagged.

[0022]FIG. 7 shows another example of maintenance information that canbe stored on a tag.

[0023]FIG. 8 shows a method for maintaining a complex article.

[0024]FIG. 9 shows a system landscape for maintaining a complex article.

[0025]FIGS. 10 and 11 show methods for maintaining a complex article.

[0026] Like reference symbols in the various drawings indicate likeelements.

DETAILED DESCRIPTION

[0027]FIG. 1 shows an example of a complex article, namely the tail ofan aircraft 100, that is tagged. Aircraft 100 includes a body frame 105that supports an engine 110. Engine 110 is a component of aircraft 100and includes a compressor 115. Compressor 115 is a component of bothengine 110 and aircraft 100. Body frame 105, engine 110, and compressor115 are all tagged with electronically-accessible tags 120, 125, 130.

[0028] Tags 120, 125, 130 are electronically-accessible in that theystore data in a machine-readable format. For example, tags 120, 125, 130can store a computer-readable globally unique identifier (“GUI”). Onesuch globally unique identifier is the Electronic Product Code (“ePC”)of the MIT (Massachusetts Institute of Technology) AutoID Center. FIG. 2illustrates the format of the ePC. Optionally, tags 120, 125, 130 canalso include a processor to process data. For example, tags 120, 125,130 can be smart cards or other devices that include a processor forprocessing information.

[0029] An interrogator (not shown) is a device for reading data fromtags 120, 125, 130. The interrogator may also write to tags 120, 125,130. Tags 120, 125, 130 can be, e.g., active and passive RFID tags,integrated circuit (“IC”) microprocessor cards and memory cards, opticalmemory cards, barcodes, molecular tags, smart cards, or othercomputer-readable storage devices that include information relating tothe identification of body frame 105, engine 110, and compressor 115,respectively. The interrogator can be any device capable of reading fromtags 120, 125, 130 such as, e.g., an optical scanner, a transceiver, amolecular reader, a card reader, a card-accepting device, or otherdevice for reading data that can be interfaced with a computer.

[0030] Additionally, tags 120, 125, 130 can include a user-interfacedevice. The user-interface device can be part of the tag or be aseparate device that is coupled to the tag. Such a user-interface devicecan include, e.g., an input device for sending information to the tags120, 125, 130 and a display for displaying data read from tags 120, 125,130. An operator can use a user-interface device to read data from tags120, 125, 130 without relaying the read data to remote locations, orwithout writing additional information to tags 120, 125, 130.

[0031] Tags 120, 125, 130 can also store information related to theoperation, maintenance, repair, replacement, and technicalcharacteristics of the respective components to which they are attached(i.e., body frame 105, engine 110, and compressor 115). As shown inFIGS. 3, 4, and 5, information 300, 400, 500 can include operatingenvironment information associated with the body frame 105, engine 110,and compressor 115. In particular, information 300 includes examples ofoperation records 305, maintenance records 310, and technicalcharacteristics 315 relating to aircraft 100 that can be stored in tag120 mounted to body frame 105. Information 300 also include information320 that identifies relationships between aircraft 100, engine 110, andcompressor 115. For example, information 320 can identify thehierarchical relationship between aircraft 100 and components engine 110and compressor 115 at different times.

[0032] Likewise, information 400 includes examples of operation records405, maintenance records 410, and technical characteristics 415 relatingto engine 110 that can be stored in tag 125 mounted to engine 110, andinformation 500 includes examples of operation records 505, maintenancerecords 510, and technical characteristics 515 relating to compressor115 that can be stored in tag 130 mounted to compressor 115.

[0033] Information included in the technical characteristics 515, forexample, can be: information describing procedures and technicalspecifications for performing preventive and corrective maintenance, theprerequisites to performing the maintenance (for example, safetyrequirements including safety tagging and electrical isolation,radiological controls requirements, and cleanliness requirements), andmiscellaneous information describing the maintenance (such as the toolsand equipment needed to do the maintenance, qualification of theoperator or mechanic who is going to do the maintenance, and the timeneeded to perform the maintenance). Alternatively, the describedinformation can be stored elsewhere, such as within information 300,400, 500.

[0034] A tag can also receive information from a sensor that senses atrait of the article or a component of the article. As shown in FIG. 6,an aircraft 600 includes a fuel level sensor 605 that measures theamount of fuel 610 in a fuel tank 615. Fuel tank 615 is a component ofaircraft 600 and is tagged with a tag 620 that receives informationabout the amount of fuel 610 from fuel level sensor 605 over acommunication line 625. Data from fuel level sensor 605 can be stored inraw form on tag 620, or a processor can process the data from fuel levelsensor 605 to determine, e.g., the fuel consumed during a particulartrip. For example, either tag 620 or sensor 605 can include such aprocessor. The processed results can be stored on tag 620.

[0035] In order to identify when a trip has been completed or to receiveother information related to the operation, maintenance, repair,replacement, and technical characteristics of aircraft 600, tag 620 canalso receive information from sources other than fuel level sensor 605.For example, tag 620 can receive information over a communication line630 from an antenna 635 mounted to aircraft 600. Antenna 635 canwirelessly receive, e.g., information about the current location ofplane 600 and local weather conditions.

[0036] Information can be stored on the tags such as tags 120, 125, 130,610 in open formats, closed formats, or a combination of both. FIG. 7illustrates information 700 that is potentially stored on a tag, andcharacteristics of the format in which portions of information 700 arestored. In particular, information 700 includes operation records 705,maintenance records 710, and technical characteristics 715 that relateto a tagged article or a tagged component of an article. Operationrecords 705 and maintenance records 710 are stored in closed formats, asindicated by locked icons 715. Technical characteristics 715 are storedin open formats, as indicated by unlocked icons 720. Example openstandards include the rich text format (“RTF”), the extensible markuplanguage (“XML”) over the hypertext transfer protocol (“HTTP”), theportable document format (“PDF”) standard, the American Standard Codefor Information Interchange (“ASCII”), and post-script files. Examplesof closed standards include proprietary formats.

[0037] A tag can be mechanically coupled to a component by a variety ofways. For example, the tag can be coupled by using fasteners, adhesives,welding, or any combination thereof. Devices such as the describeduser-interface device and the sensor can be similarly coupled to thecomponent or the tag.

[0038]FIG. 8 shows an example of a method 800 for tracking, operating,and maintaining a complex article using one or moreelectronically-accessible tags coupled to one or more components of thecomplex article. An interrogator performing method 800 first retrieves aGUI or other identifier that identifies a first component of the complexarticle (step 805). The identifier is retrieved from anelectronically-accessible tag that is coupled to the component. Theinterrogator can retrieve the ID, e.g., by optically or electronicallyscanning the tag.

[0039] The interrogator also retrieves maintenance information from thetag (step 810). The maintenance information can include, e.g., ahistorical record of maintenance that has been performed on thecomponent, a historical record of the past operation of the component,or information related to procedures for maintaining the component. Theinformation can be stored in an open standard or in a closed standard.

[0040] If necessary, the retrieved maintenance information can berecorded so that the information is made available separately from thetag (step 815). For example, the retrieved maintenance information canbe relayed to a central database system for storage or analysis.Recording the retrieved information separately from the tag creates aback-up copy of the maintenance information, and allows analyses thatrequire increased amounts of processing power or information fromdisparate information sources to be performed. Examples of disparateinformation sources include multiple electronically-accessible tagscoupled to the components of a complex article, as well as multipleelectronically-accessible tags distributed throughout a fleet of complexarticles.

[0041] The interrogator, or a human user operating the interrogator,makes a decision as to whether or not a maintenance operation is to beperformed (decision 820). The maintenance operation can be performed onthe tagged component, or on another component of the article. Thedecision can be based on the time since the last maintenance operationwas performed, the operational history of the component, or combinationsof these and other factors. The decision can be based on the servicehours of a component. The decision can also be based on information fromdisparate, multiple, electronically-accessible tags.

[0042] If it is decided to perform the maintenance operation, theninstructions for performing the maintenance operation can be retrievedfrom the electronically-accessible tag, if needed (step 825). Forexample, the volume of oil that lubricates an engine can be retrievedfrom a tag mounted to the engine. This capability minimizes the chancethat maintenance is delayed while maintenance instructions are located,or that incorrect maintenance instructions are inadvertently used. Themaintenance operation can then be performed (step 830). The performancecan be based on the retrieved instructions, as appropriate.

[0043] A second decision is made as to whether the last component of thearticle has been interrogated, or if the interrogation is to end(decision 835). This decision can be made by a user, or it can be madeby the interrogator or other processing system based on information thatidentifies a relationship between one or more components of an articleand the article itself, and/or one or more components of a component andthe component itself. If it is decided that the last component has beeninterrogated, then method 800 ends.

[0044] Alternatively, if it is decided that additional components are tobe interrogated, then the interrogator retrieves a GUI or otheridentifier that identifies another component of the complex article(step 840) and again retrieves maintenance information regarding thenext component and decides whether maintenance is necessary.

[0045] Maintenance information need not be retrieved from the samecomponent upon which a maintenance operation is performed, or from whichmaintenance instructions are retrieved. For example, informationrelating to the fuel usage of an engine in a single engine motor vehiclecan be retrieved from an electronically-accessible tag on a fuel tank,while instructions for adjusting the operation of an engine can beretrieved from an electronically-accessible tag on the body frame.

[0046] The following describes an example implementation of method 800.Aircraft 100 described above is flying from Frankfurt to San Franciscowith a two-hour stop over in Washington D.C. As the aircraft 100 landsin Washington D.C., an operator, such as an engine mechanic, who isresponsible for maintenance of the aircraft can interrogate tag 125 todetermine which, if any, preventive maintenance can be performed onengine 110 during the two-hour stop over. The operator can use aninterrogator such as the one described above or, alternatively, caninterface with tag 125 through a user-interface device that is coupledto or included with tag 125. Tag 125 includes information that specifyall preventive maintenance for engine 110. The information can, forexample, specify the preventive maintenances that have not beenperformed for the current maintenance cycle and are due. The operatorprovides information that specify resources available to perform themaintenance. Such information can include the qualification of themechanic, the maintenance equipment locally available to perform themaintenance, as well as any time constraints such as the two-hour limit.Such information can be stored in the interrogator. Using informationstored on tag 125 and information provided by the operator, tag 125determines which preventive maintenance, if any, can be performed duringthe stop over and presents these maintenance options to the operator.Alternatively, the interrogator can retrieve maintenance informationfrom tag 125, make the determination, and present the options to theoperator. In response to a selection from the operator, the tag providesthe appropriate procedures and technical specifications for performingthe selected maintenance. When the operator completes the maintenance,the operator stores a record of the maintenance completion in tag 125.

[0047] As shown in FIG. 9, a system landscape 900 can include multiple,independent systems using methods and apparatus, including computerprogram products, for maintaining a complex article in accordance withthe invention. In particular, system landscape 900 includes a tag 905, acollection of interrogators 910, 915, 920, 925, and a collection ofsystems 930, 935, 940, 945. Tag 905 is coupled to a component 950 of acomplex article 955 and can store information that identifies tag 905,as well as maintenance records, operational records, and technicalcharacteristics of component 950 and/or complex article 955.

[0048] Interrogator 910 and system 930 are operated by a manufacturer ofcomplex article 955 or a manufacturer of component 950. Interrogator 910can write to tag 905. System 930 contains information and instructionsrelating to the maintenance of component 950 and/or complex article 955,and for providing component 950 with an identifier. For example, system930 can include a database that stores technical information about theoperation and maintenance of component 950 and instructions forperforming maintenance operations on component 950.

[0049] Interrogator 915 and system 935 are operated by a distributor ofcomplex article 955 or component 950. Interrogator 915 can read from tag905. System 935 contains information relating to the distribution ofcomponent 950 and/or complex article 955. For example, system 950 caninclude a database that includes information relating to the location ofcomponent 950 as it moves through a distribution system.

[0050] Interrogator 920 and system 940 are operated by an operator ofcomplex article 955 that includes component 950. Interrogator 920 canwrite to and read from tag 905. System 940 contains information andinstructions relating to the maintenance of component 950 and/or complexarticle 955, and for tracking component 950 as it changes locationsduring operation. For example, system 940 can include a database thatstores information about the performance of maintenance operations uponcomponent 950, the operational records of component 950, as well asoperational records, maintenance records, and location records of othercomponents.

[0051] Interrogator 925 and system 945 are operated by a maintainer oftagged component 950 and/or complex article 955. Interrogator 925 canwrite to and read from tag 905. System 945 contains information andinstructions relating to the maintenance of component 950 and/or complexarticle 955, and for tracking component 950 as it changes locationsduring operation. For example, system 945 can include a database thatstores information about the performance of maintenance operations uponcomponent 950, the operational records of component 950, as well asoperational records, maintenance records, and location records of othercomponents.

[0052] Any of the roles described above need not be present in a systemlandscape in accordance with the invention. For example, a manufacturercan also distribute tagged component 950, or an operator can alsomaintain tagged component 950 or complex article 955. Furthermore,additional roles not described above can be included in the systemlandscape. For example, a retailer can transfer the complex article fromthe distributor to the operator, more than one operator can operate asingle tagged component 950 or complex article 955, or more than onemaintainer can maintain a single tagged component 950 or complex article955.

[0053] Complex article 955 can include more than one component and morethan one component tag. In this case, complex article 955 can include ageneral tag. The general tag includes information that describe thecomplex article as a whole. Such information can include a hierarchy ofthe components of complex article 955. For example, the information canspecify that one component is part of another component. Suchinformation can also include maintenance information for the complexarticle as a whole. For example, the general tag can include a log ofcomponent replacement and, furthermore, can identify a particularcomponent even when the particular component and its tag has beenremoved from complex article 955. The general tag can also include logicand data for and managing and prioritizing the maintenance of allcomponents of complex article 955. For example, the logic and data canspecify that maintenance on a vital component is more important toperform than maintenance on a non-vital component. Alternatively, allinformation included in the general tag can be stored on component tags.A component tag can include information that describes all or part ofthe component hierarchy.

[0054]FIG. 10 shows an example method 1000 by which systems 930, 935,940, 945 interact with a tag such as tag 905. During the performance ofmethod 1000, manufacturer system 930 writes a globally unique identifierto tag 905 (step 1005) and technical information about the component totag 905 (step 1010). The GUI and technical information can be writtenafter or before tag 905 is mounted to the component. For example, theGUI and technical information can be written to tag 905 g in a read-onlyformat during manufacture of tag 905. The GUI and technical informationcan be written, e.g., in an open standard.

[0055] At some point the manufacturer transfers the tagged component toa distributor. The tagged component can be provided as a stand aloneelement, or as a component of an assemblage of components such as acomplex article. Distributor system 935 reads tag 905 and identifies thecomponent from the GUI (step 1015). Distributor system 935 recordslocation information that identifies the location of tag 905, and hencethe location of the tagged component (step 1020).

[0056] The distributor can now move and track the tagged componentthrough a distribution system. For example, the distributor can move thetagged component from a central warehouse to a regional distributioncenter. To track tag 905, distributor system 935 again reads the GUIfrom tag 905 (step 1025) and records location information thatidentifies the location of tag 905 and the tagged component (step 1030).If the GUI is in an open standard, then the distributor need not requirespecialized equipment or licenses to track the component in thedistribution system.

[0057] At some point the distributor transfers the tagged component toan operator. The tagged component can be provided as a stand aloneelement, or as a component of an assemblage of components such as acomplex article. Operator system 940 reads tag 905 and identifies thecomponent from the GUI (step 1035). Operator system 940 records locationinformation that identifies the location of tag 905, and hence thelocation of the tagged component (step 1040). Operator system 940 canrepeatedly read the GUI from tag 905 and record location information totrack the tagged component as it moves through an operation system. Forexample, operator system 940 can track the location of a tagged aircraftengine as it moves from plane to plane, and from airport to airport.

[0058] Operator system 940 can also read technical information about thecomponent from tag 905 (step 1045) and apply the read technical info asappropriate (step 1050). For example, operator system 940 can read thetechnical characteristics of the component from the tag to determine ifthe component is compatible with other components in a complex article.

[0059] At some point, the operator of the tagged component will placethe tagged component in service. Operation records describing the natureof the service can be written to tag 905. For example, as discussedabove, a sensor that is mounted to the component, or another componentof a complex article, can write records to tag 905. Alternatively,operator system 940 can write operation records to tag 905 (step 1055).For example, operator system 940 can write the identities orcharacteristics of other components in a complex article to tag 905.Operator system 940 can write also write other operation records, suchas, e.g., location information or performance information, to tag 905.

[0060] The operation records can be written by operator system 940 usinga closed standard. This can prevent others from accessing or changingthe operational records of the tagged component without theauthorization of the operator.

[0061] Operator system 940 can also read operation records about theoperation of the tagged component from tag 905 (step 1060) and apply theread operation records as appropriate (step 1065). For example, operatorsystem 940 can apply the read operation records to retrieve sensormeasurements to determine the operational behavior of the taggedcomponent or to compare the operational behavior of the taggedcomponents to the expected operational behavior. Operator system 940 canalso apply the read operation records to determine when maintenance ofthe tagged component is needed.

[0062] At some point, the operator will transfer the tagged component toa maintainer. For example, an airline that operates an aircraft with atagged engine can allow a maintenance organization to inspect andmaintain the aircraft. Maintainer system 945 reads tag 905 andidentifies the component from the GUI (step 1070). Maintainer system 945can also read technical information about the component from tag 905(step 1075) and apply the read technical info as appropriate (step1080). For example, maintainer system 945 can read instructions formaintaining the tagged component from tag 905, and display theinstruction for use in performing a maintenance operation.

[0063] Maintainer system 945 can also read operation records about theoperation of the tagged component from tag 905 (step 1085) and apply theread operation records as appropriate (step 1090). For example,maintainer system 945 can apply the read operation records to determinewhen maintenance of the tagged component is needed and the type ofmaintenance operation that is to be performed. Maintainer system 945 canapply the read operation records by, e.g., displaying the operationrecords to a user who makes a decision as to whether maintenance isnecessary or by relaying the operation records to a processor that makesa maintenance decision based on predetermined rules.

[0064] Maintainer system 945 can also write maintenance records to tag905 (step 1092). For example, maintainer system 945 can write the datethat a certain maintenance operation has been performed, or the resultsof a maintenance or inspection operation. The maintenance records can bewritten by maintainer system 945 using a closed standard. The closedstandard can be shared with others as desired. For example, an operatorand one or more maintainers can use a common closed format for operationand maintenance records. This can prevent others from accessing andchanging the maintenance records of the tagged component without theauthorization of the operator and/or the maintainer.

[0065] Maintainer system 945 can also read maintenance records about themaintenance of the tagged component from tag 905 (step 1094) and applythe read maintenance records as appropriate (step 1096). For example,operator system 940 can apply the read maintenance records to determinewhen maintenance or inspection of the tagged component is needed and thetype of maintenance or inspection operation that is to be performed.Maintainer system 945 can apply the read maintenance records by, e.g.,displaying the maintenance records to a user who makes a decision as towhether maintenance is necessary or by relaying the maintenance recordsto a processor that makes a maintenance decision based on predeterminedrules or artificial intelligence approaches.

[0066] As discussed above, when the complex article includes more thanone component and more than one component tag, either the component tagsor a general tag can include information that describes the complexarticle as a whole. An interrogator can thus retrieve such informationfrom either a general tag or a component tag.

[0067]FIG. 11 shows an example method 1100 by which a company or otherentity can profit from the maintenance of a complex article thatincludes a tagged component. In particular, an entity can select anopen, public format for the storage of information upon a tag (step1105). The entity can also develop a closed standard for the storage ofinformation upon the tag (step 1110). The entity can also define whichinformation is to be stored in the selected open format upon the tag,and which information is to be stored in the closed standard upon thetag (step 1115). The definition can be performed by the entity itself,or in conjunction with a manufacturer of the component that is to betagged. The results of the definition can reflect a need for securingcertain information. For example, the definition can define thatidentifying information is to be stored in an open format, whilemaintenance records are to be stored in a closed format to preventunauthorized users from reading and writing maintenance records.

[0068] The entity can also arrange for the manufacture of a tag with thedefined open and closed formats and information, as well as the couplingof the tag to a component of a complex article (step 1120). The entitycan arrange for the manufacture by, e.g., manufacturing the tag itselfor by licensing a design to a tag manufacturer. Similarly, the tag canbe coupled to the component by the entity, a tag manufacturer, or acomponent manufacturer.

[0069] The entity can also license the closed standard for data to anoperator of the complex article (step 1125). The license, for example,can allow all maintenance employees of the operator to use the standard.

[0070] The entity can also license the closed standard for data to oneor more maintainers of the complex article (step 1130). In this case,the license can be sold to the businesses that the operator of thecomplex articles has employed to perform the maintenance.

[0071] By licensing the closed standard to operators and/or maintainers,the entity can receive an income stream even when no new tag purchasesare made. Moreover, since tags can be designed to be robust and survivefor many years, the income stream can be used to offset the cost of thecapital investment in the tags.

[0072] The invention can be implemented in digital electronic circuitry,or in computer hardware, firmware, software, or in combinations of them.The invention can be implemented as a computer program product, i.e., acomputer program tangibly embodied in an information carrier, e.g., in amachine-readable storage device or in a propagated signal, for executionby, or to control the operation of, data processing apparatus, e.g., aprogrammable processor, a computer, or multiple computers. A computerprogram can be written in any form of programming language, includingcompiled or interpreted languages, and it can be deployed in any form,including as a stand-alone program or as a module, component,subroutine, or other unit suitable for use in a computing environment. Acomputer program can be deployed to be executed on one computer or onmultiple computers at one site or distributed across multiple sites andinterconnected by a communication network.

[0073] Method steps of the invention can be performed by one or moreprogrammable processors executing a computer program to performfunctions of the invention by operating on input data and generatingoutput. Method steps can also be performed by, and apparatus of theinvention can be implemented as, special purpose logic circuitry, e.g.,an FPGA (field programmable gate array) or an ASIC (application-specificintegrated circuit).

[0074] Processors suitable for the execution of a computer programinclude, by way of example, both general and special purposemicroprocessors, and any one or more processors of any kind of digitalcomputer. Generally, a processor will receive instructions and data froma read-only memory or a random access memory or both. The essentialelements of a computer are a processor for executing instructions andone or more memory devices for storing instructions and data. Generally,a computer will also include, or be operatively coupled to receive datafrom or transfer data to, or both, one or more mass storage devices forstoring data, e.g., magnetic, magneto-optical disks, or optical disks.Information carriers suitable for embodying computer programinstructions and data include all forms of non-volatile memory,including by way of example semiconductor memory devices, e.g., EPROM,EEPROM, and flash memory devices; magnetic disks such as internal harddisks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROMdisks. The processor and the memory can be supplemented by, orincorporated in special purpose logic circuitry.

[0075] To provide for interaction with a user, the invention can beimplemented on a computer having a display device such as a CRT (cathoderay tube) or LCD (liquid crystal display) monitor for displayinginformation to the user and a keyboard and a pointing device such as amouse or a trackball by which the user can provide input to thecomputer. Other kinds of devices can be used to provide for interactionwith a user as well; for example, feedback provided to the user can beany form of sensory feedback, such as visual feedback, auditoryfeedback, or tactile feedback; and input from the user can be receivedin any form, including acoustic, speech, or tactile input.

[0076] A number of embodiments of the invention have been described.Nevertheless, it will be understood that various modifications may bemade without departing from the spirit and scope of the invention. Forexample, the steps of the invention can be performed in a differentorder and still achieve desirable results. Accordingly, otherembodiments are within the scope of the following claims.

What is claimed is:
 1. A method for storing maintenance information onan electronically-accessible tag that is coupled to an article, themethod comprising: storing maintenance information in both a first andsecond format in the electronically-accessible tag, the first formatbeing in accordance with an open standard and the second format being inaccordance with a closed standard.
 2. The method of claim 1, furthercomprising: storing maintenance information in a format that is deviceindependent.
 3. The method of claim 1, wherein storing maintenanceinformation in the first format includes: storing the maintenanceinformation in a format that is in accordance with one of RTF, ASCII,and PDF.
 4. The method of claim 1, wherein storing maintenanceinformation in the second format includes: storing the maintenanceinformation in a format that is proprietary and that can only beaccessed by proprietary devices.
 5. The method of claim 1, furthercomprising: retrieving the maintenance data; and updating the format ofthe maintenance data; and storing the maintenance data with the updatedformat in the electronically-accessible tag.
 6. The method of claim 1,wherein storing maintenance data includes: storing maintenanceprocedures and technical specifications related to the article.
 7. Themethod of claim 1, wherein storing maintenance information includes:storing a first type of maintenance information in the first format: andstoring a second type of maintenance information in the second format.8. The method of claim 7, wherein storing a first type of maintenanceinformation in the first format includes: storing maintenance logs inthe first format; and storing maintenance procedures and technicalspecifications in the second format.
 9. The method of claim 1, whereinstoring maintenance information includes: storing maintenanceinformation of a component of one of an aircraft, a sea going vessel,and a vessel that travels on land.
 10. An electronically-accessible tag,comprising: memory that includes maintenance data of a first and asecond format, the first format being in accordance with an openstandard and the second format being in accordance with a closedstandard.
 11. The electronically-accessible tag of claim 10, wherein:the first format is device independent.
 12. Theelectronically-accessible tag of claim 10, wherein: the first format isin accordance with one of RTF, ASCII, and PDF.
 13. Theelectronically-accessible tag of claim 10, wherein: the second format isa proprietary format.
 14. The electronically-accessible tag of claim 10,wherein: the maintenance data includes maintenance procedures andtechnical specifications of an article.
 15. Theelectronically-accessible tag of claim 10, further comprising: an inputand output device for sending maintenance data and receiving updatedmaintenance data.
 16. The electronically-accessible tag of claim 10,further comprising: a processor and logic for updating the first andsecond format.
 17. The electronically-accessible tag of claim 10,wherein: maintenance data of the first format includes maintenance logs;and maintenance data of the second format includes maintenanceprocedures and technical specifications.
 18. Theelectronically-accessible tag of claim 10, wherein: the tag is coupledto one of an aircraft, a sea going vessel, and a vessel that travels byland; and the maintenance data stored in the memory includes maintenancedata of one or more components of the aircraft, sea going vessel, orvessel that travels by land.